Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Blocked Days Calculation - Output Date Format #59

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dbdailey
Copy link
Contributor

@dbdailey dbdailey commented Aug 2, 2018

This is a feature to calculate the blocked days by specifying an attribute representing a block. For example, the Blocked attribute can be specified and it will calculate the amount of time that the issue was/is blocked.

This is a feature to calculate the blocked days by specifying an attribute representing a block.  For example, the Blocked attribute can be specified and it will calculate the amount of time that the issue was/is blocked.
- Multiple block and unblocks are allowed.
- When enabled, the block values are used in the ScatterPlot, Cycle Time Histogram, and Flow Efficiency.
o Cycle Time:
 issues are displayed as a red dot instead of a black dot.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is not proper markdown and does not render correctly.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll work on fixing it and providing the correct markdown.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cool, thanks! Not a super big deal, but thought I'd call it out.

@@ -129,6 +145,8 @@ Criteria:
- User Story
Start Date: 2001-01-23
End Date: 2019-12-30
BlockedAttributes: Blocked, Blocked-In Progress

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are "blocked" and "blocked-in progress" workflow states, or is this looking at the "Flagged" attribute in JIRA?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So, the way this works is that it will evaluate each field in the change log and if it matches any of the entries in the BlockedAttributes criteria, it will calculate the number of blocked days based upon the on/off of that field value. I believe that if you wanted to calculate the blocked days based upon the "Flagged" condition, you would just put the field "Impediment" in the BlockedAttributes section. Like this: BlockedAttributes: Impediment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Understood, unfortunately, that is not working for me. I tried adding Impediment, Flagged, Blocked, and none worked. There is no Blocked Days column being added to the output file.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

okay, I'll see what I can do. I'll test specifically with Impediment and Flagged.

@@ -113,6 +113,22 @@ The Criteria Section of the config file is simply named "Criteria" (without the
- Filters: a list of the names of the filters you want to apply
- Start Date: a date filter in the format YYYY-MM-DD which will exclude issues with resolved dates before the provided date (optional)
- End Date: a date filter in the format YYYY-MM-DD which will include issues with resolved dates before the provided date (optional)
- BlockedAttributes: This optional feature will add and value the ‘Days Blocked’ column to the CSV extract with the number of days blocked for each issue.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is not adding a "Days Blocked" column to my output.csv file, is it only going to add the column if there is data returned, or should it at least return 0 for every issue (with or without blocked data)?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The Days Blocked column will only be added if there is a field listed in the BlockedAttributes section of the Criteria. If it is not configured, then it will not put the column in the output. Also, I believe that it will not put anything in the csv for blocked days if an issue has not been "blocked" Of course, the definition of blocked is really that configurable field (i.e. Impediment). I'm totally okay will defaulting to 0 if no blocked data is present for an issue. Is that perferred? Let me know and I'll work on changing it.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it would be great if it would default to 0 if there is no blocked data rather than just having a null field. This could also signify that the addition of the "BlockedAttributes" option was successful.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay, I'll look into make the change and defaulting.

@samiller2013
Copy link

samiller2013 commented Aug 20, 2018 via email

@jpiaggio
Copy link

jpiaggio commented Dec 3, 2018

@samiller2013 I'm looking for this Blocked days feature, do we know when the PullRequest will be approved?

@samiller2013
Copy link

@jpiaggio no idea, I'm not from ActionableAgile unfortunately.

@samiller2013
Copy link

@johnrjj - would you mind reviewing and approving some of the PRs? Do you have any thoughts on how we could get the blocked days calculation to work?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants